An i-model is a container for rich, multi-discipline information published from known sources in a known state at a certain point in time. Each i-model is:

• A published version of this information, provided as a secure, read-only file.
• Portable, combining all information into a single container for easy distribution.
• Self-describing, because you can view the design without having the application with which it was created.
• A semantically rich data file that contains the related business information from the design applications, as well as the graphics.
• An interoperable deliverable tailored for change management.
• Used for information exchange throughout all phases of a project´s life cycle.

Project information from different applications often must be shared. An i-model is used to exchange project information from different applications and products. For example, an i-model allows you to share Bentley data along with third-party product information. An i-model shows a design at a precise state, facilitating the review and management of the design. Because it is a snapshot of the design, it can be used in many different types of workflows.

The i-model combines all the graphics and business data intelligence, as defined by the design application, into a single deliverable container for distribution. Because an i-model optimizes the business data, the result is decreased file size and easier navigation. An i-model contains links back to the original source data from which the i-model was derived, facilitating the life cycle review workflow. An i-model has an .I.DGN or .IMODEL extension.

An i-model does not require any special application to open and use the I.DGN file. It is a read-only file, which prevents any corruption to the source file and it keeps the information secure. An i-model shows the design at a certain state, which makes it useful for version control and iterative workflows. The i-model is designed for information reuse.